In lightningdevkit/vss-server#101 we dropped the
Java version of `vss-server` and moved the Rust version to the repo
root. Here we account for the updated location in our integration tests.

Read and write BDK wallet state through async KVStore helpers while
keeping the current WalletPersister entry points bridged through the
node runtime. This reduces the wallet persistence surface that still
depends on KVStoreSync.

Co-Authored-By: HAL 9000

Static invoice persistence already runs from async handlers, so use
KVStore directly instead of routing those reads and writes through
the blocking KVStoreSync trait.

Co-Authored-By: HAL 9000

Persist peer store updates through async KVStore operations. The
synchronous node APIs keep bridging at their runtime boundary while
async event handling awaits peer persistence directly.

Co-Authored-By: HAL 9000

Persist DataStore mutations through async KVStore operations while
keeping the existing synchronous APIs bridged through the node
runtime. Async event handling now awaits payment store writes
directly.

Co-Authored-By: HAL 9000

Persist node metric updates through async KVStore writes and await
them from the chain, gossip, and scoring tasks. This removes the
remaining blocking metrics writer while keeping the helper name
stable.

Co-Authored-By: HAL 9000

Avoid introducing a temporary macro when moving node metrics persistence onto async KV storage.

Co-Authored-By: HAL 9000

Persist the on-chain wallet through BDK's AsyncWalletPersister so
wallet state writes use the async KVStore path. Existing synchronous
wallet APIs keep bridging through the node runtime until their
callers are made async.

Co-Authored-By: HAL 9000

Open filesystem stores through the async LDK migration helper so
v1-to-v2 store migration no longer depends on the blocking KVStoreSync
migration path.

Co-Authored-By: HAL 9000

Move the existing in-memory test store into a shared module without
changing its behavior. This lets integration tests reuse it while
keeping the later async TestSyncStore change separate.

Co-Authored-By: HAL 9000

Keep the shared test store move as a pure code move by restoring the original comments and spacing.

Co-Authored-By: HAL 9000

Exercise async KVStore operations in TestSyncStore and filesystem
migration tests while keeping the temporary sync comparison path until
the final KVStoreSync removal. Also route pathfinding score export
through async KVStore reads.

Co-Authored-By: HAL 9000

Drop the remaining synchronous KV store trait bounds and
implementations. After the preceding migrations, custom stores only
need to provide async KVStore persistence.

Co-Authored-By: HAL 9000

Compile the VSS persistence tests after the shared KV store helper moved to async persistence.

Co-Authored-By: HAL 9000

Resolve the VSS schema through async setup on the caller runtime so
VSS stores no longer create or retain a Tokio runtime.

NodeBuilder preserves fail-fast setup while the VSS builder stays
synchronous.

Co-Authored-By: HAL 9000

Construct PostgreSQL storage on the caller runtime now that the store
only exposes async KVStore operations. This removes the store-owned
runtime and its shutdown path.

Co-Authored-By: HAL 9000

Run the existing payments benchmark once per configured store backend so
filesystem, SQLite, and optional PostgreSQL results are reported under the
same payment flow.

AI-assisted-by: OpenAI Codex

Wait for the cleanup payment to settle before starting the next payment
benchmark sample. This keeps the measured forward-payment duration intact
while avoiding HTLC state leaking into later samples.

AI tools: Created with assistance from OpenAI Codex.

Add an operations bench target with a forwarding benchmark that compares
sqlite, filesystem, and postgres stores over a settled multi-hop payment.

AI-assisted-by: OpenAI Codex

Add a channel-open benchmark that measures the open_channel call while
leaving chain confirmation cleanup outside the timed section.

AI-assisted-by: OpenAI Codex

Add a startup benchmark that restarts a node whose store already contains
channel and payment data, so startup cost reflects persisted node state.

AI-assisted-by: OpenAI Codex

AI-Assisted-By: OpenAI Codex